feat(examples): adopt persistent app releases - #30
Draft
jona62 wants to merge 5 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Move eleven examples to persistent app releases with app-local dependencies, declared dependency inputs, and managed CLI entrypoints. Pin n8n to the deployed 2.22.6 version and use separate persistent app data. Twenty examples with system-level installers explicitly retain image replacement and its review requirements.
Validated all 31 manifests and the eleven incremental plans with the updated CLI. Four Python health checks, the Codex launcher, and n8n lockfile validation pass locally. Live installation, storage, and rollback verification remains pending; this draft must follow the core server/CLI rollout. Existing app ownership and data are not automatically migrated.